feat: move WTI structural persistence off mutation path - #50
Merged
pathscale merged 2 commits intoAug 4, 2026
Conversation
pathscale
force-pushed
the
feat/logical-index-persistence
branch
from
August 4, 2026 23:53
18d9f52 to
1908f6b
Compare
pathscale
force-pushed
the
feat/logical-index-persistence
branch
from
August 4, 2026 23:54
1908f6b to
788c8ee
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Correctness and compatibility
Local performance probe
Ten interleaved ARM trials, 2,000,000 existing-key mutations and 8,000,000 point reads per trial:
These are engineering probes, not publication numbers. Generated-table select measurements still need a quiet-window campaign before making a sub-percent claim.
Verification
Stacking note
This branch is based on current master after PR 47 and PR 49. Against PR 48 head b76a60a, the combined tree compiles with all features and the concurrent logical-WTI reload test passes. The current cherry-pick has one mechanical src/lib.rs export-list conflict because PR 48 has not yet rebased onto current master; there is no implementation conflict with its in-place update path.